Video Title: Building my startup in public
Video ID: KOWbe77O6aw
Video URL: https://www.youtube.com/watch?v=KOWbe77O6aw
Export Date: 2025-11-07 01:43:43
Channel: Will Wang
Format: markdown
================================================================================

📹 **Video Information**:

**Title**: Building my startup in public
**Channel**: Will Wang
**Duration**: 22:07
**Views**: 14,882


## Overview
This video documents the recent experiences of two startup founders as they navigate the challenges of launching their AI-powered video editing product, fundraising, and building in public. It covers lessons learned from fundraising, product development, going viral, and the importance of networking in the San Francisco startup ecosystem.

## Main Topics Covered

- Startup fundraising experiences and strategies
- The impact and aftermath of going viral during a product launch
- Product development cycles and user feedback
- Building a personal brand and distributing content publicly
- The value of being in San Francisco for startups
- Community, networking, and attending tech events
- Actionable advice for founders building in public

## Key Takeaways & Insights

- **Fundraising is a numbers and momentum game:** Successful fundraising requires a large top-of-funnel (many VC meetings) and tightly packed meetings to maintain momentum. Losing momentum significantly slows down the process.
- **Rejection is normal:** Founders should expect and prepare for numerous rejections (“nos”) before getting a lead investor. Closing the first investor often unlocks others to follow.
- **Going viral is double-edged:** While virality can validate demand and attract users or investors, it can be mentally taxing to have large numbers of people use an unpolished product. However, real-world user data is invaluable for product direction.
- **Build in public, but focus:** Start with one social media platform, master it, and expand only when ready. Most people fail by spreading themselves too thin or worrying too much about early quality.
- **San Francisco accelerates growth:** Being physically present in SF provides access to networks, spontaneous meetings, and cutting-edge tech conversations that are hard to replicate elsewhere.
- **Product and user validation are separate:** Getting sign-ups and interest is not enough; ongoing, continuous usage is what truly validates a product.

## Actionable Strategies

- **Condense fundraising:** Schedule as many VC meetings as possible within a short window (e.g., two weeks) to maintain momentum and avoid a drawn-out process.
- **Embrace rejection:** Normalize hearing “no” and see it as part of the journey. View each pitch as practice and an opportunity to refine your story.
- **Launch early, iterate fast:** Don’t wait for perfection—launch a minimal viable product (MVP), collect user feedback, and iterate rapidly.
- **Focus your public building:** Choose one platform (YouTube, Twitter, etc.), consistently create content, and only worry about quality and optimization after 10–15 pieces are published.
- **Network intentionally:** Attend local events, meet other founders, and immerse yourself in the startup scene to unlock opportunities and learning.
- **Validate with real usage:** Prioritize continuous user engagement and retention over vanity metrics like sign-up numbers or viral views.

## Specific Details & Examples

- The startup’s launch video went viral: 750,000+ views on Twitter, 200,000 on Threads, and 100,000 on Instagram, resulting in significant VC interest and $100K raised (with an initial target of $1M).
- Fundraising involved 30–40 VC calls, but the founders believe 100+ would have been needed for better results.
- The product allows users to edit videos using text prompts rather than traditional timelines, aiming to streamline the editing process for content creators.
- After going viral, the team received valuable feedback but also faced the challenge of not having a fully polished product, which affected user retention.
- Networking in San Francisco enabled spontaneous meetings with major tech companies (e.g., Adobe) and other founders, greatly accelerating learning and opportunities.
- Building in public started with YouTube, then expanded to Twitter, with advice to avoid trying to master all platforms simultaneously.
- Anecdotes about other founders and tools (e.g., Gabber, a dev tool that remained online during major outages) reinforce the value of resilience and community.

## Warnings & Common Mistakes

- **Dragging out fundraising:** Spreading meetings over too long leads to lost momentum and lower success rates.
- **Treating VC meetings like job interviews:** Founders should lead the conversation rather than just answer questions.
- **Launching with only a waitlist:** Waitlists often decay, leading to lost momentum and interest.
- **Being too quality-obsessed early:** Over-optimizing early content or product polish delays feedback and growth.
- **Relying only on sign-up numbers:** Without continuous usage and retention, initial demand is not meaningful.
- **Avoiding networking/events:** Over-focusing on solo work limits exposure to ideas and opportunities.

## Resources & Next Steps

- **Product access:** The MVP is live for users to test and provide feedback.
- **Attend tech events:** Founders encourage attending launch parties, demo days, and local meetups.
- **Join communities:** The founders mention their Discord and recommend networking at places like Founders Inc. in San Francisco.
- **Follow founders on social media:** For ongoing updates and advice on building in public, follow them on YouTube and Twitter.
- **Try complementary tools:** Mention of Gabber for developers and VR productivity gear (as discussed in the video) may interest viewers.
- **Continue iterating:** The team plans to further develop the product, add a paywall, and relaunch based on user feedback.

---

This summary synthesizes the founders’ journey, highlighting actionable insights for early-stage startup founders, particularly those interested in fundraising, product-market fit, and building a personal brand in the tech ecosystem.